Unified metadata search

ABSTRACT

Metadata associated with content stored in a corresponding primary storage system is received receiving from each secondary storage cluster of a plurality of different secondary storage clusters included in different storage domains. The metadata received from the plurality of different secondary storage clusters is stored and indexed together. A unified metadata search interface is provided for stored data of the corresponding primary storage systems and the plurality of different secondary storage clusters of the different storage domains.

BACKGROUND OF THE INVENTION

A storage domain may be comprised of a primary storage system and asecondary storage cluster. A user associated with the storage domain mayremotely access and manage the primary storage system and/or thesecondary storage cluster via a remote connection (e.g., virtual privatenetwork connection). An enterprise may be associated with a plurality ofstorage domains having different physical locations. The user mayremotely access and manage each of the plurality of storage domains,however, a separate remote connection with a separate interface is oftenrequired for each of the storage domains.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating a system for providing a unifiedmetadata search interface and a central storage management interface fora plurality of storage domains in accordance with some embodiments.

FIG. 2 is a diagram illustrating an embodiment of a storage domain.

FIG. 3 is a flow chart illustrating a process for providing a unifiedmetadata search interface in accordance with some embodiments.

FIG. 4 is a flow chart illustrating a process for performing a searchusing a unified metadata search interface in accordance with someembodiments.

FIG. 5 is a flow chart illustrating a process for performing a backupjob in accordance with some embodiments.

FIG. 6 is a block diagram illustrating a central storage managementinterface in accordance with some embodiments.

FIG. 7 is a flow chart illustrating a process for providing a userinterface in accordance with some embodiments.

FIG. 8 is a flow chart illustrating a process for performing a backupjob in accordance with some embodiments.

FIG. 9 is a diagram illustrating a system for registering a storagecluster in accordance with some embodiments.

FIG. 10 is an example of a process for registering a storage cluster inaccordance with some embodiments.

FIG. 11 is a diagram illustrating a timeline for registering a storagecluster in accordance with some embodiments.

FIG. 12 is an example of a user interface in accordance with someembodiments.

FIG. 13 is an example of a user interface in accordance with someembodiments.

FIG. 14 is an example of a user interface in accordance with someembodiments.

FIG. 15 is an example of a user interface in accordance with someembodiments.

FIG. 16 is an example of a user interface in accordance with someembodiments.

FIG. 17 is an example of a user interface in accordance with someembodiments.

FIG. 18 is an example of a user interface in accordance with someembodiments.

DETAILED DESCRIPTION

An enterprise may be associated with a plurality of storage domainslocated at different locations. For example, a first storage domain maybe located in New York, a second storage domain may be located in LosAngeles, a third storage domain may be located in Singapore, and afourth storage domain may be located in Paris. A storage domain may becomprised of a primary storage system and a storage cluster. Eachstorage domain may store a plurality of files and different types offiles (e.g., virtual machines, database files, content files, etc.).

A user associated with the enterprise may desire to remotely searchcontent associated with the plurality of storage domains. The user mayestablish a separate virtual private network (VPN) connection to each ofthe plurality of storage domains to search content associated with aparticular storage domain. However, this requires separate searches oneach of the plurality of storage domains. The user may desire todetermine whether multiple copies of a particular file is stored in theplurality of storage domains, but to perform such a determination, theuser would have to search each individual storage domain and determinewhether the particular file is stored in each of the storage domains.

The user associated with the enterprise may be able to perform a globalsearch of the plurality of objects (e.g., file, virtual machine (VM),database, server, etc.) associated with the plurality of storage domainsusing a unified metadata search interface associated with a cloudservice system. For example, the user may search for a particular filevia the unified metadata search interface and the cloud service systemmay notify the user of the one or more storage domains that store a copyof the particular file.

The user associated with the enterprise may register with the cloudservice system one or more storage clusters. A storage cluster of astorage domain may store a backup of one or more objects stored on orpreviously stored on a primary storage system of the storage domain. Insome embodiments, the storage cluster is configured to be a secondarystorage system for the primary storage system. In other embodiments, thestorage cluster is configured to be a storage system for a userassociated with the storage cluster (e.g., directly store one or moreobjects generated on the storage cluster). The storage cluster of thestorage domain may have access to metadata associated with a pluralityof objects stored in the primary storage system. For example, theprimary storage system may provide the storage cluster a list of one ormore objects stored on the primary system. The list may include themetadata associated with the one or more objects. The storage clustermay provide to the cloud service system metadata associated with aplurality of objects stored in the primary storage system and metadataassociated with a plurality of objects stored in the storage cluster.The storage clusters associated with one or more other storage domainsof the enterprise may also provide to the cloud service system metadataassociated with a plurality of objects stored in the correspondingprimary storage system and metadata associated with a plurality ofobjects stored in the corresponding storage cluster.

In response to receiving the metadata from one or more storage clusters,the cloud service system may perform an ETL (extract, transform, load)process on the received metadata and consolidate a result of the ETLprocess in an index that is searchable by a search engine (e.g., adistributed multitenant-capable full-text search engine). This mayenable a user associated with the enterprise to perform a global searchof the plurality of objects associated with the plurality of storagedomains using a unified metadata search interface associated with thecloud service system.

A storage cluster may initially send to the cloud service system all ofthe metadata associated with a plurality of objects stored in theprimary storage system and all of the metadata associated with aplurality of objects stored in the storage cluster. The cloud servicesystem may generate a searchable index based on the metadata, however,the searchable index may become out-of-date because one or more objectsin the primary storage system and/or the storage cluster may besubsequently deleted, modified, or added.

To ensure that the searchable index is up-to-date within a thresholdduration (e.g., 15 minutes), the storage cluster may be configured toprovide the metadata associated with a plurality of objects stored inthe primary storage system and the metadata associated with a pluralityof objects stored in the storage cluster according to an update policy.Each storage cluster may have its own corresponding update policy andmay provide metadata to the cloud service system at different rates. Theupdate policy may indicate that a storage cluster is configured toprovide to the cloud service system the metadata associated with aplurality of objects stored in the primary storage system and themetadata associated with a plurality of objects stored in the storagecluster on a periodic basis (e.g., every five minutes, every tenminutes, every fifteen minutes, etc.). The update policy may indicatethat an incremental set of metadata is to be provided to the cloudservice system after the initial set of metadata. The storage clustermay reduce the amount of bandwidth used to send the metadata to thecloud service system from the storage cluster by sending an incrementalset of metadata instead of sending the full set of metadata. Sending anincremental set of metadata may also reduce the overall amount of timeto keep the searchable index up-to-date because the cloud storage systemmay be processing less data to update the searchable index. The metadatato be included in the incremental set of metadata may be determinedbased on a timestamp associated with the metadata. For example, thestorage cluster may provide the metadata for objects having a timestamplater than a timestamp associated with a last update. In someembodiments, the update policy indicates that a storage cluster isconfigured to provide to the cloud service system the metadataassociated with a plurality of objects stored in the primary storagesystem and the metadata associated with a plurality of objects stored inthe storage cluster after a threshold amount of metadata has changed. Insome embodiments, the update policy indicates that a storage cluster isconfigured to provide to the cloud service system the metadataassociated with a plurality of objects stored in the primary storagesystem and the metadata associated with a plurality of objects stored inthe storage cluster in response to a command from a user associated withthe enterprise. In other embodiments, the update policy indicates that astorage cluster is configured to provide to the cloud service system themetadata associated with a plurality of objects stored in the primarystorage system and/or the metadata associated with a plurality ofobjects stored in the storage cluster any time the metadata associatedwith a plurality of objects stored in the primary storage system or themetadata associated with a plurality of objects stored in the storagecluster has changed.

A user associated with an enterprise may be able to use a unifiedmetadata search interface associated with the cloud service system toperform a global search for any object in the one or more storagedomains associated with the enterprise. The cloud service system maysearch for the object using one or more metadata attributes associatedwith an object. The one or more metadata attributes associated with anobject may include, but are not limited to, file name, network name,internet protocol (IP address), VM type, application type, applicationname, operating system (OS) name, OS type, date backed up, file size,location (e.g., which system stores the object), etc. A unified metadatasearch interface of the cloud service system may, for example, receivefrom a user associated with an enterprise, a request for one or moreobjects associated with an OS of Windows 10. In response to the request,the cloud service system may determine the one or more objectsassociated with the OS of Windows 10 and provide via the unifiedmetadata search interface associated with the cloud service system anotification of the one or more determined objects.

Previously, a user associated with the enterprise had to be physicallyon-premises at a storage domain to cause the one or more backup jobsassociated with the one or more objects of the storage domain to beperformed. However, the cloud service system may enable the userassociated with the enterprise to remotely cause the one or more backupjobs associated with the one or more objects of the storage domain to beperformed. In addition to providing a unified metadata search interface,the cloud service system may provide a central storage managementinterface for a plurality of different storage clusters included indifferent storage domains and receive an indication of a storage cluster(e.g., a selection). In response to the indication, the cloud servicesystem may provide an indication of the one or more available backupjobs associated with the indicated storage cluster. The one or moreavailable backup jobs may be different depending upon the indicatedstorage cluster because the storage clusters associated with anenterprise may have different backup capabilities. For example, a firststorage cluster may be associated with a first version of a storagecluster and a second storage cluster may be associated with a secondversion of the storage cluster. The one or more available backup jobsassociated with the first version of the storage cluster may bedifferent than the one or more available backup jobs associated with thesecond version of the storage cluster. The second version of the storagecluster may include the one or more available features (e.g., backupjobs) associated with the first version of the storage cluster and oneor more features not available with the first version of the storagecluster, e.g., the second version of the storage cluster is an upgradeof the first version of the storage cluster.

The central storage management interface of the cloud service system mayenable a user associated with the enterprise to remotely access anyregistered storage cluster associated with the enterprise. The cloudservice system may provide a user interface for an indicated storagecluster. A registered storage cluster may be a particular version of thestorage cluster. Each version of the storage cluster may have adifferent version of a native user interface. Providing a user interfacethat is different from the user interface of an indicated storagecluster may confuse the user associated with the enterprise. Forexample, the user may desire to perform a particular backup job via thecentral storage management interface. The on-premises storage clustermay provide a particular user interface that requires the user tointeract with the particular user interface in a particular manner tocause the particular backup job to be performed. If the central storagemanagement interface associated with the cloud service system isprovided a different user interface, then the user associated with theenterprise may waste time interacting with the central storagemanagement interface to figure out how to cause the particular backupjob to be performed. In a worst case scenario, the user associated withthe enterprise may give up and decide against performing the particularbackup job because the central storage management interface associatedwith the cloud service system was too confusing.

The cloud service system may provide a central storage managementinterface that is configured to provide the version of the native userinterface associated with an indicated storage cluster. When a userassociated with an enterprise registers a storage cluster with the cloudservice system, the storage cluster may provide configurationinformation associated with the storage cluster to the cloud servicesystem. The configuration information may include native user interfaceversion information associated with the storage cluster. The cloudservice system may store corresponding user interface code associatedwith each user interface version of the storage cluster.

The cloud service system may provide a central storage managementinterface that provides an overview screen that displays a list ofavailable storage clusters. The central storage management interface mayreceive an indication (e.g., selection) of a storage cluster from a userassociated with an enterprise. In response to the indicated storagecluster, the cloud service system may determine a version of the nativeuser interface associated with the indicated storage cluster, load theuser interface code associated with the determined native user interfaceversion, and remotely execute the determined version of the native userinterface. The central storage management interface may provide a userinterface that enables a user associated with the enterprise to interactwith the central storage management interface associated with the cloudservice system as if the user were local to the user interface of theindicated storage cluster. This may also reduce any user interfaceconfusion the user may encounter because the user interface provided bythe central storage management interface is the same user interface asthe indicated storage cluster.

A user associated with the enterprise may use the central storagemanagement interface associated with the cloud service system to causean indicated storage cluster to perform one or more backup commands. Thecloud service system may be comprised of a UI service virtualizationcontainer, a caching service virtualization container, and a pluralityof persistent connection virtualization containers. The central storagemanagement interface associated with the cloud service system may beprovided by comprised of a UI service virtualization container. Thecaching service virtualization container may store a data structure thatassociates a persistent connection virtualization container with aparticular storage cluster. A persistent connection virtualizationcontainer may be configured to maintain bidirectional communicationsbetween the cloud service system and a storage cluster. Each storagecluster may be associated with a corresponding persistent connectionvirtualization container.

In response to receiving one or more commands via the central storagemanagement interface of the cloud service system, the UI servicevirtualization container may be configured to request from a cachingservice virtualization container an identifier associated with apersistent connection virtualization container corresponding to theindicated storage cluster. The caching service virtualization containermay respond to the request by inspecting (e.g., a lookup) a datastructure stored by the caching service virtualization container toidentify a persistent connection virtualization container associatedwith the indicated storage cluster. For example, the caching servicevirtualization container may determine an IP address of a persistentconnection virtualization container that is associated with theindicated storage cluster. The caching service virtualization containermay then provide the UI service virtualization container the identifier(e.g., IP address) associated with the persistent connectionvirtualization container corresponding to the indicated storage cluster.The UI service virtualization container may provide the one or morecommands to the persistent connection virtualization containerassociated with the indicated storage cluster having the identifier. Thepersistent connection virtualization container associated with theindicated storage cluster may then forward the one or more commands tothe indicated storage cluster, which in response to receiving the one ormore commands, is configured to perform one or more backup jobs based onthe one or more commands.

FIG. 1 is a block diagram illustrating a system for providing a unifiedmetadata search interface and a central storage management interface fora plurality of storage domains in accordance with some embodiments. Inthe example shown, system 100 is comprised of storage domain 101,storage domain 111, storage domain 121, cloud environment 132 thatincludes a cloud service system 131, and user device 142.

An enterprise may be associated with n storage domains located atdifferent locations. For example, an enterprise may be associated withstorage domain 101, storage domain 111, and storage domain 121. Eachstorage domain may be comprised of a primary storage system and astorage cluster. In the example shown, storage domain 101 is comprisedof primary storage system 103 and storage cluster 104, storage domain111 is comprised of primary storage system 113 and storage cluster 114,and storage domain 121 is comprised of primary storage system 123 andstorage cluster 124. In some embodiments, a storage domain is associatedwith cloud storage (not shown). A storage cluster of the storage domainassociated with cloud storage may have a list of one or more objectsassociated with the storage domain that are stored in cloud storage. Insome embodiments, a storage domain may include a plurality of storageclusters.

Primary storage systems 103, 113, 123 are computing systems that storefile system data. The file system data may be comprised of a pluralityof objects (e.g., file, virtual machine (VM), database, server, etc.)and metadata associated with the plurality of objects. Primary storagesystems 103, 113, 123 may be comprised of one or more servers, one ormore computing devices, one or more storage devices, and/or acombination thereof. In some embodiments, a primary storage system mayprovide a corresponding storage cluster a list of one or more objectsstored on the primary storage system. The list may include the metadataassociated with the one or more objects.

A storage cluster may cause the primary storage system to perform abackup snapshot of the file system data according to a backup policy andsend the backup snapshot to the storage cluster. A backup snapshot mayrepresent the state of the primary storage system at a particular pointin time (e.g., the state of the file system data). The backup snapshotpolicy may require a full backup snapshot or an incremental backupsnapshot to be performed. A full backup snapshot includes the entirestate of the primary storage system at a particular point in time. Anincremental backup snapshot includes the state of the primary storagesystem that has changed since a last backup snapshot. Storage clusters104, 114, 124 may cause primary storage systems 103, 113, 123,respectively, to perform a backup snapshot of the file system data. Insome embodiments, the storage cluster is configured to be a secondarystorage system for the primary storage system.

A primary storage system may store one or more virtual machines. Eachvirtual machine may have an associated IP address. A primary storagesystem, such as primary storage systems 103, 113, 123, may provide to acorresponding storage cluster, such as storage cluster 103, 113, 123, alist of one or more IP addresses associated with one or more virtualmachines. In some embodiments, a corresponding storage cluster maycommunicate with a virtual machine associated with an IP addressincluded in the provided list. A corresponding storage cluster may backup the virtual machine associated with the IP address, determine the oneor more objects associated with the backed up virtual machine, andgenerate an index of the one or more determined objects associated withthe backed up virtual machine. The index may include one or moremetadata attributes associated with the one or more determined objectsassociated with the backed up virtual machine.

A storage cluster may be comprised of a plurality of storage nodes. Eachstorage node may have a corresponding processor. A storage cluster mayingest the file system data and store the file system data across theplurality of storage nodes. For example, storage clusters 104, 114, 124may be comprised of a corresponding plurality of storage nodes and storethe file system data received from a corresponding primary storagesystem and across the corresponding plurality of storage nodes. In someembodiments, a storage cluster is configured to be a secondary storagecluster for a corresponding primary storage system. In otherembodiments, a storage cluster is configured to be a main storagecluster for a user associated with the storage cluster. A storagecluster may be configured to store a plurality of objects generated by auser associated with the storage cluster (e.g., directly store one ormore objects generated on the storage cluster). In other embodiments, astorage cluster is configured to be a secondary storage cluster for acorresponding primary storage system and a main storage cluster for auser associated with the storage cluster. A storage cluster may maintaina metadata store that is configured to store the metadata associatedwith the plurality of objects stored in the storage cluster. In someembodiments, a single storage node is implemented instead of a storagecluster.

A user associated with storage domains 101, 111, 121 may individuallyregister storage domains 101, 111, 121 with cloud service system 131 toenable the user associated with storage domains 101, 111, 121 toremotely access and manage the storage domains. Cloud service system 131may enable a user to remotely access and manage storage domains that arephysically located separately throughout the world from a singlelocation. A user may register a storage cluster of a storage domain withcloud service system using a cluster registration procedure, forexample, using the procedure described herein.

Storage clusters 104, 114, 124 may be located behind correspondingfirewalls. Storage clusters 104, 114, 124 may initiate communicationswith cloud service system 131, but the corresponding firewalls areinitially configured to prevent cloud service system 131 from initiatingcommunications with storage clusters 104, 114, 124. For example, cloudservice system 131 may send corresponding requests to storage clusters104, 114, 124, but storage clusters 104, 114, 124 won't send a reply tothe corresponding request because the corresponding firewalls will blockthe request. To manage storage domains 101, 111, 121 via cloud servicesystem 131, cloud service system 131 needs to initiate communicationswith storage clusters 104, 114, 124. Bidirectional communications 110,120, 130 may be established between storage clusters 104, 114, 124 andpersistent connection virtualization containers 133 a, 133 b, 133 c,respectively. Establishing persistent bidirectional communicationsbetween a storage cluster and cloud service system 131 may beestablished, for example, using the procedure as described in Assignee'sU.S. patent application U.S. Ser. No. 16/226,366, the entire contents ofwhich are herein incorporated by reference. Persistent connectionvirtualization containers 133 a, 133 b, 133 c may be used to maintainpersistent connection pipes 110, 120, 130 between storage clusters 104,114, 124, and cloud service system 131. Persistent connectionvirtualization containers 133 a, 133 b, 133 c may be part of accessservice 152. Cloud service system may be comprised of a plurality ofaccess services, each access services comprised of a plurality ofpersistent connection virtualization containers.

Caching service virtualization container 136 may record and preserve astate associated with bidirectional communications. For example, thestate may include an IP address associated with a persistent connectionvirtualization container, a storage domain to which the persistentconnection virtualization container is associated, a storage clusteridentifier associated with a storage cluster, a clusterID, etc. Eachtime a persistent connection virtualization container establishesbidirectional communications with a storage cluster (e.g., initialbidirectional communication or re-establishing bidirectionalcommunications), the persistent connection virtualization container maybe configured to provide its associated state to caching servicevirtualization container 136.

Cloud service system 131 may be running in cloud environment 132. Cloudenvironment 132 may be a public cloud or a private cloud. For example,cloud environment 132 may be an Amazon Web Services cloud, a MicrosoftAzure cloud, a Google cloud, etc.

A storage cluster may provide to cloud service system 131 metadataassociated with content stored in a corresponding storage domain. Astorage cluster may provide to cloud service system 131 metadataassociated with a plurality of objects stored in the storage cluster anda plurality of objects stored in a primary storage system associatedwith the storage cluster. For example, storage cluster 104 may provideto cloud service system 131, metadata associated with a plurality ofobjects stored in storage cluster 104 and a plurality of objects storedin primary storage system 103. Storage cluster 114 may provide to cloudservice system 131, metadata associated with a plurality of objectsstored in storage cluster 114 and a plurality of objects stored inprimary storage system 113. Storage cluster 124 may provide to cloudservice system 131, metadata associated with a plurality of objectsstored in storage cluster 124 and a plurality of objects stored inprimary storage system 123.

In response to receiving the metadata from storage clusters 104, 114,124, cloud service system 131 may perform an ETL (extract, transform,load) process on the received metadata using ETL virtualizationcontainer 137 and consolidate a result of the ETL process in an indexthat is searchable by search index virtualization container 138. Thismay enable a user associated with the enterprise to perform a globalsearch of the plurality of objects associated with storage domains 101,111, 121 using a unified metadata search interface of cloud servicesystem 131.

Storage clusters 104, 114, 124 may initially send to cloud servicesystem 131 all of the metadata associated with a plurality of objectsstored in primary storage systems 103, 113, 123 and all of the metadataassociated with a plurality of objects stored in storage clusters 104,114, 124, respectively. Cloud service system 131 may generate asearchable index based on the metadata, however, the searchable indexmay become out-of-date because one or more objects in primary storagesystems 103, 112, 123 and/or storage clusters 104, 114, 124 may besubsequently deleted, modified, or added.

To ensure that the searchable index is up-to-date within a thresholdduration (e.g., 15 minutes), storage cluster 104, 114, 124 may beconfigured to provide the metadata associated with a plurality ofobjects stored in primary storage systems 103, 113, 123 and the metadataassociated with a plurality of objects stored in storage clusters 104,114, 124, respectively, according to an update policy. The update policymay indicate that a storage cluster is configured to provide to cloudservice system 131 the metadata associated with a plurality of objectsstored in the primary storage system and the metadata associated with aplurality of objects stored in the storage cluster on a periodic basis(e.g., every five minutes, every ten minutes, every fifteen minutes,etc.). The update policy may indicate that an incremental set ofmetadata is to be provided to cloud service system 131 after the initialset of metadata. Sending an incremental set of metadata instead ofsending the full set of metadata may reduce the amount of bandwidth usedto send the metadata to cloud service system 131 from the storagecluster. It may also reduce the overall amount of time to keep thesearchable index up-to-date because cloud service system 131 may beprocessing less data to update the searchable index. The metadata to beincluded in the incremental set of metadata may be determined based on atimestamp associated with the metadata. In some embodiments, the updatepolicy indicates that a storage cluster is configured to provide tocloud service system 131 the metadata associated with a plurality ofobjects stored in the primary storage system and the metadata associatedwith a plurality of objects stored in the storage cluster after athreshold amount of metadata has changed. In some embodiments, theupdate policy indicates that a storage cluster is configured to provideto cloud service system 131 the metadata associated with a plurality ofobjects stored in the primary storage system and the metadata associatedwith a plurality of objects stored in the storage cluster in response toa command from a user associated with the enterprise. In otherembodiments, the update policy indicates that a storage cluster isconfigured to provide to cloud service system 131 the metadataassociated with a plurality of objects stored in the primary storagesystem and/or the metadata associated with a plurality of objects storedin the storage cluster any time the metadata associated with a pluralityof objects stored in the primary storage system or the metadataassociated with a plurality of objects stored in the storage cluster haschanged.

Cloud service system 131 may include UI service virtualization container134. UI service virtualization container 134 may be configured toprovide a user interface. The user interface may include a unifiedmetadata search interface. A user associated with an enterprise may beable to use the unified metadata search interface associated with cloudservice system 131 via user device 142 to perform a global search forany object in storage domains 101, 111, 121. User device 142 may be acomputing device, such as a laptop, a desktop, a server, a smartphone, acellular phone, a mobile device, a tablet, etc. User device 142 mayinclude an application or a web browser capable of communicating withcloud service system 131 via connection 140. Connection 140 may be awired or wireless connection.

Cloud service system 131 may search for the object using one or moremetadata attributes associated with an object. The one or more metadataattributes associated with an object may include, but are not limitedto, file name, network name, internet protocol (IP address), VM type,application type, application name, operating system (OS) name, OS type,date backed up, file size, location (e.g., which system stores theobject), etc. UI service virtualization container 134 may, for example,receive from a user associated with an enterprise, a request for one ormore objects with one or more metadata attributes (e.g., a particularfile name). In response to the request, cloud service system 131 maydetermine the one or more objects associated with the one or moremetadata attributes (e.g., particular filename) and provide via the userinterface associated with UI service virtualization container 134 anotification of corresponding locations for the one or more determinedobjects associated with the one or more metadata attributes. In otherembodiments, cloud service system 131 may forward the request to one ormore registered storage clusters (e.g., storage clusters 104, 114, 124).In response to the request, a registered storage cluster may determineif there are any objects stored in the storage domain associated withthe registered storage cluster that match the one or more metadataattributes associated with an object. The registered storage cluster mayprovide one or more search results to cloud service system 131, which inresponse, is configured to provide the one or more search results touser device 142 via a user interface provided by UI servicevirtualization container 134. Cloud service system 131 may not collectcertain types of metadata, e.g., filename, from one or more registeredstorage clusters because the amount of data associated with the type ofmetadata is too voluminous. For example, an enterprise may be associatedwith a billion files. Cloud service system 131 may provide a unifiedmetadata search interface for a plurality of enterprises. Storing thefilename for a billion files per enterprise may require a large amountof cloud storage space. Cloud service system 131 may selectivelydetermine the type of metadata that is provided from a registeredstorage cluster to cloud service system 131. In the event cloud servicesystem 131 receives a requests for a metadata attribute that is notindexed by cloud service system 131, cloud service system 131 mayforward the request to one or more registered storage clusters. This mayreduce the amount of cloud storage space used by cloud service system131, but increase the amount of time needed for cloud service system 131to service the search request.

Previously, a user associated with the enterprise had to be physicallyon-premises at storage domains 101, 111, 121 to cause the one or morebackup jobs associated with the one or more objects of storage domains101, 111, 121 to be performed. However, cloud service system 131 mayenable the user associated with the enterprise via user device 142 toremotely cause the one or more backup jobs associated with the one ormore objects of storage domains 101, 111, 121 to be performed.

The user interface provided by UI service virtualization container 134of cloud service system 131 may include a central storage managementinterface. UI service virtualization container 134 may receive via userdevice 142 an indication (e.g., a selection) of one of the storageclusters 104, 114, 124. In response to the indication, UI servicevirtualization container 134 may provide an indication of the one ormore available backup jobs associated with the indicated storagecluster. The one or more available backup jobs may be differentdepending upon the indicated storage cluster because the storageclusters associated with an enterprise may have different backupcapabilities. For example, storage cluster 104 may be associated with afirst version of a storage cluster and storage cluster 114 may beassociated with a second version of the storage cluster. The one or moreavailable features associated with the first version of the storagecluster may be different than the one or more available featuresassociated with the second version of the storage cluster. Storagecluster 114 may include the one or more available features associatedwith the storage cluster 104 and one or more available features notavailable with storage cluster 104, e.g., storage cluster 114 is anupgrade of storage cluster 104.

The central storage management interface associated with UI servicevirtualization container 134 may enable a user associated with theenterprise via user device 142 to remotely access any registered storagecluster associated with the enterprise (e.g., storage clusters 104, 114,124). UI service virtualization container 134 may provide a native userinterface version associated with an indicated storage cluster. Forexample, the native user interface may be provided to a web browser orapplication of user device 142. Each registered storage cluster may beassociated with a different version of the storage cluster. Each versionof the storage cluster may have a different native user interface.Providing a user interface that is different from the user interface ofan indicated storage cluster may confuse the user associated with theenterprise. For example, the user may desire to perform a particularbackup job. The on-premises storage cluster may provide a particularuser interface that requires the user to interact with the particularuser interface in a particular manner to cause the particular backup jobto be performed. If the user interface provided by UI servicevirtualization container 134 is different than the user interfaceprovided by the indicated storage cluster, then the user associated withthe enterprise may waste time interacting with the user interfaceprovided by UI service virtualization container 134 to figure out how tocause the particular backup job to be performed. In a worst casescenario, the user associated with the enterprise may give up and decideagainst performing the particular backup job because the user interfaceprovided by UI service virtualization container 134 was too confusing.

UI service virtualization container 134 may be configured to provide theversion of the native user interface associated with an indicatedstorage cluster. When a user associated with an enterprise registers astorage cluster with cloud service system 131, the storage cluster mayprovide configuration information associated with the storage cluster tocloud service system 131. The configuration information may includeversion information associated with the storage cluster. Cloud servicesystem 131 may store a corresponding user interface code associated witheach user interface version of the storage cluster.

UI service virtualization container 134 may provide a central storagemanagement interface that displays a list of available storage clusters.UI service virtualization container 134 may receive an indication of astorage cluster from a user associated with an enterprise via userdevice 142. In response to the indicated storage cluster, UI servicevirtualization container 134 may determine a native user interfaceversion associated with the indicated storage cluster and load the userinterface code associated with the version of the native user interfaceof the indicated storage cluster. The native user interface may beaccessed via a portion of the central storage management interface. Thismay enable the user associated with the enterprise to interact with thecentral storage management interface as if the user were local to theuser interface of the indicated storage cluster. This may also reduceany user interface confusion the user may encounter.

A user associated with the enterprise may use the user interfaceassociated with UI service virtualization container 134 via user device142 to cause an indicated storage cluster to perform one or more backupcommands. In response to receiving one or more commands, UI servicevirtualization container 134 may be configured to request from cachingservice virtualization container 136 an identifier associated with apersistent connection virtualization container corresponding to theindicated storage cluster. Caching service virtualization container 136may respond to the request by inspecting (e.g., a lookup) a datastructure stored by caching service virtualization container 136 toidentify a persistent connection virtualization container associatedwith the indicated storage cluster (e.g., persistent connectionvirtualization container 133 a, persistent connection virtualizationcontainer 133 b, or persistent connection virtualization container 133c). For example, caching service virtualization container 136 maydetermine an IP address of a persistent connection virtualizationcontainer that is associated with the indicated storage cluster. Cachingservice virtualization container 136 may then provide UI servicevirtualization container 134 the identifier (e.g., IP address)associated with the persistent connection virtualization containercorresponding to the indicated storage cluster. UI servicevirtualization container 134 may provide the one or more commands to thepersistent connection virtualization container associated with theindicated storage cluster having the identifier. The persistentconnection virtualization container associated with the indicatedstorage cluster (e.g., persistent connection virtualization container133 a, persistent connection virtualization container 133 b, orpersistent connection virtualization container 133 c) may then forwardthe one or more commands to the indicated storage cluster (e.g., storagecluster 104, storage cluster 114, or storage cluster 124), which inresponse to receiving the one or more commands, is configured to performone or more backup jobs based on the one or more commands.

In some embodiments, the plurality of virtualization containersassociated with cloud service system 131 (e.g., UI servicevirtualization container 134, caching service virtualization container136, search index virtualization container 138, ETL virtualizationcontainer 137, persistent connection virtualization containers 133 a,133 b, 133 c) are hosted on one of the storage clusters associated withan enterprise (e.g., storage cluster 104, storage cluster 114, storagecluster 124). The storage cluster hosting the plurality ofvirtualization containers may act as a master storage cluster for theenterprise. A user associated with the enterprise may register one ormore other storage clusters with the master storage cluster. The masterstorage cluster may be configured to receive metadata associated withone or more other storage domains and provide the same services as cloudservice system 131 (e.g., a user interface, a unified metadata searchinterface, a management interface). Management associated with theenterprise (e.g., a government agency, a financial institution, a lawfirm, etc.) may have concerns about storing enterprise data andenterprise information in a cloud environment using cloud service system131. The enterprise data and enterprise information may be stored usinga master storage cluster instead of cloud service system 131. The masterstorage cluster may provide the same functionality as described hereinas cloud service system 131.

FIG. 2 is a diagram of illustrating an embodiment of a storage domain.In the example shown, storage domain 200 includes primary storage system202 and storage cluster 204 connected via network 203. Storage domain200 may be implemented in at least one of the storage domains 101, 111,121 of FIG. 1 .

Primary storage system 202 is a computing system that stores file systemdata. Primary storage system 202 may be comprised of one or moreservers, one or more computing devices, one or more storage devices,and/or a combination thereof. In response to one or more commandsreceived from storage cluster 204, primary storage system 202 mayperform a backup snapshot of the one or more storage volumes of primarystorage system 202 to storage cluster 204.

The backup snapshot may be a full backup snapshot or an incrementalbackup snapshot. Each storage volume of the primary storage system iscomprised of file system data. File system data may be comprised of aplurality of objects. A full backup snapshot includes a copy of theentire file system data of the storage volume to be backed up. Anincremental backup snapshot stores the file system data that was notpreviously backed up.

Primary storage system 202 may be configured to backup file system datato storage cluster 204 according to one or more backup policiesassociated with storage cluster 204. In some embodiments, a backuppolicy indicates that file system data is to be backed up on a periodicbasis (e.g., hourly, daily, weekly, monthly, etc.). In otherembodiments, a backup policy indicates that file system data is to bebacked up when a threshold size of data has changed. In otherembodiments, a backup policy indicates that file system data is to bebacked up upon a command from a user associated with primary storagesystem 202. For example, a user associated with primary storage system202 may cause a backup snapshot to be performed via a cloud servicesystem. The file system data may be sent from primary storage system 202to storage cluster 204 via a network 203. Network 203 may be one or moreof the following: a local area network, a wide area network, a wirednetwork, a wireless network, the Internet, an intranet, or any otherappropriate communication network.

Storage cluster 204 is configured to receive and backup file system datafrom primary storage system 202. Storage cluster 204 is configured tostore the file system data and organize the file system data in a treedata structure. An example of the tree data structure is a snapshot tree(e.g., Cohesity Snaptree), which may be based on a B+ tree structure (orother type of tree structure in other embodiments). The file system datamay include metadata associated with the file system data, a pluralityof content files, and metadata associated with the content files. Thestorage cluster may create a file system metadata snapshot tree for thebackup snapshot. The metadata associated with the plurality of contentfiles may be organized using a snapshot tree and stored in a key valuestore (KVS). The file system metadata snapshot tree for the backupsnapshot corresponds to a version of the storage volume(s) at aparticular moment in time. The storage cluster may also create a filetree corresponding to a content file included in the backup snapshot.The file tree is a file metadata structure. The file tree may store themetadata associated with the file corresponding to the file tree. A leafnode of the file system metadata snapshot tree may include a pointer toone of the file trees, linking the contents of a content file to thefile system metadata snapshot tree. A leaf node of a file tree mayinclude a pointer to a brick storing one or more data chunks associatedwith a content file. A leaf node of the snapshot tree may be configuredto store a key-value pair of metadata. The key-value pairs of metadata(e.g., log sequence numbers, file name, creation date, offline/onlinestatus, etc.) may be stored in the KVS.

A file system metadata snapshot tree is a tree data structure and iscomprised of a root node, one or more levels of intermediate nodes, andone or more leaf nodes. In some embodiments, a file system metadatasnapshot tree is comprised of a root node and one or more leaf nodes.The root node is the starting point of a file system metadata snapshottree and may include pointers to one or more other nodes. The root nodeincludes an identifier that indicates a view (e.g., backup snapshot)with which the root node is associated. An intermediate node is a nodeto which another node points (e.g., root node, other intermediate node)and includes one or more pointers to other nodes. A leaf node is a nodeat the bottom of a file system metadata snapshot tree. In someembodiments, a leaf node is configured to store key-value pairs of filesystem metadata associated with the storage volume(s). In someembodiments, a leaf node includes a pointer to a file tree. For example,a leaf node of a file system metadata snapshot tree storing metadataassociated with the storage volume(s) may include a pointer to a rootnode of a file tree storing data associated with a content file. In someembodiments, a leaf node of a file system metadata snapshot tree or aleaf node of a file tree includes a pointer to or an identifier of abrick identifier associated with one or more data chunks of the file. Adata brick may be associated with one or more chunk identifiers (e.g.,SHA-1). A chunk metadata table may store information that associates abrick identifier with one or more chunk identifiers and one or morechunk file identifiers. A chunk file metadata table may associate achunk file identifier with a chunk file storing a plurality of datachunks. The chunk metadata table and the chunk file metadata table maybe used, based on a brick identifier, to locate the data chunksassociated with the file corresponding to the file metadata tree.

The tree data structure may be used to capture different versions of thestorage volume(s) at different moments in time. A backup snapshotreceived from a primary storage system may include data associated witha first version of the storage volume(s) at a first point in time and asubsequent backup snapshot received from the primary storage system mayinclude data associated with the second version of the storage volume(s)at a second point in time. Each version of the volume(s) may berepresented in a corresponding file system metadata snapshot tree. Thetree data structure allows a chain of file system metadata snapshottrees (i.e., each corresponding file system metadata snapshot tree) tobe linked together by allowing a node of a later version of a filesystem metadata snapshot tree corresponding to a later version of thestorage volume(s) to reference a node of a previous version of the filesystem metadata snapshot tree corresponding to an earlier version of thestorage volume(s). The tree data structure allows a chain of file trees(i.e., each corresponding file tree) to be linked together by allowing anode of a later version of a file tree corresponding to a later versionof a content file to reference a node of a previous version of the filetree corresponding to an earlier version of the content file.

Each time data for an incremental backup snapshot of the storagevolume(s) is received, a new file system metadata snapshot tree is addedto the corresponding tree data structure by creating a new root node.The new root node may be a clone of the root node associated with aprevious file system metadata snapshot tree. Initially upon creation,the new root node includes the set of pointers included in the previousroot node, that is, the new root node includes one or more pointers toan intermediate node or leaf node that was specified in the root node ofa previous file system metadata snapshot tree associated with a previousbackup. However, among other differences, the new root node includes anode identifier and a view identifier that is different than the nodeidentifier and view identifier of the previous root node. The new filesystem metadata snapshot tree may be modified to reflect the dataincluded in the backup of the storage volume(s) (e.g., adding one ormore intermediate nodes, adding one or more leaf nodes, updatingpointers associated with nodes).

A file system metadata snapshot tree is a representation of a fullyhydrated backup because it provides a complete view of the storagevolume(s) at a particular moment in time. A fully hydrated backup is abackup that is ready for use without having to reconstruct a pluralityof backups to use it. Previous systems may reconstruct a backup bystarting with a full backup and applying one or more changes associatedwith one or more incremental backups to the data associated with thefull backup. In contrast, any file stored in the storage volume at aparticular time and the file's contents, for which there is anassociated backup, may be determined from the file system metadatasnapshot tree, regardless if the associated backup snapshot was a fullbackup snapshot or an incremental backup snapshot. Creating anincremental backup snapshot may only include copying data of the storagevolume(s) that was not previously backed up. However, the file systemmetadata snapshot tree corresponding to the incremental backup snapshotprovides a complete view of the storage volume(s) at the particularmoment in time because it includes references to data of the storagevolume that was previously stored. For example, a root node associatedwith the file system metadata snapshot tree may include one or morereferences to leaf nodes associated with one or more previous backupsnapshots and one or more references to leaf nodes associated with thecurrent backup snapshot. This provides significant savings in the amountof time needed to restore or recover a storage volume and/or a database.In contrast, traditional recovery/restoration methods may requiresignificant time, storage, and computational resources to reconstruct aparticular version of a volume or database from a full backup and aseries of incremental backups.

Storage cluster 204 may be comprised of one or more solid state drives,one or more hard disk drives, or a combination thereof. Storage cluster204 may include file system manager 215. File system manager 215 isconfigured to maintain file system data in the form of nodes arranged ina tree data structure. In some embodiments, leaf nodes in the filesystem tree include key-value pairs that associate data keys with valuesin the form of particular items of file system data. File system manager215 may be configured to perform one or more modifications to a snapshottree. File system data may include data associated with one or morecontent files and metadata associated with the one or more contentfiles. The metadata may include information, such as file size,directory structure, file permissions, physical storage location of thecontent files, time of last access, time of last modification, etc. Themetadata values for the one or more content files may be stored in ametadata store, such as a KVS.

The storage cluster 204 includes a first storage node 210, a secondstorage node 212, and an nth storage node 214. In some embodiments, n isan odd number. Each storage node may include a corresponding diskstorage, a corresponding KVS, a corresponding processor, and acorresponding memory. A user associated with storage cluster 204 may loginto one of the storage nodes 210, 212, 214 and enable a process toregister storage cluster 204.

Each storage node 210, 212, 214 maintains a portion of the KVS. Thekey-value pairs of the KVS may be grouped into a plurality of buckets.Each node of the plurality of storage nodes includes a local KVS thatstores a portion of the KVS, i.e., at least one of the plurality ofbuckets. Keys may be assigned to a storage node using a hashing functionthat generally distributes keys equally across the nodes. A master nodeof the plurality of storage nodes may be configured to store a mastertable. The master table may match a key-value pair to a storage node.Storage cluster 204 may receive a file operation (e.g., write/readoperation). The master node may inspect the master table and direct thefile operation to the storage node associated with the file operation,i.e., the node that will handle the file operation.

At least one storage node in storage cluster 204 may be designated as abackup node for the portion of the KVS that is stored on another storagenode of the storage cluster 204. For example first storage node 210 maystore keys k₁₁ to k_(1n). At least one copy of keys k₁₁ to k_(1n) may bestored on the second storage node 212, the nth storage node 214, or anyof the storage nodes between the second storage node 212 and the nthstorage node 214. This provides fault tolerance and consistency for thedistributed computing system in the event of a node failure. Multiplecopies of keys may be stored across multiple storage nodes to increasethe fault tolerance of the distributed computing system. In someembodiments, each key of the KVS is stored across a majority of thestorage nodes.

FIG. 3 is a flow chart illustrating a process for providing a unifiedmetadata search interface in accordance with some embodiments. In theexample shown, process 300 may be implemented by a cloud service system,such as cloud service system 131.

At 302, metadata associated with content stored in a plurality ofdifferent storage domains is received. An enterprise may be associatedwith a plurality of storage domains located at different locations. Eachstorage domain may have an associated storage cluster. A user associatedwith the enterprise may register one or more storage clusters associatedwith the enterprise.

A storage domain may be comprised of a primary storage system and astorage cluster. Each storage cluster may have a metadata store thatindicates the one or more objects stored by the storage cluster. Eachstorage cluster may have access to a corresponding primary storagesystem and determine the one or more objects stored by the storagecluster.

In some embodiments, each of the registered storage clusters provide allof the metadata associated with the content stored in the primarystorage system and all of the metadata associated with the contentstored in the registered storage cluster.

In other embodiments, each of the registered storage clusters providethe metadata associated with content stored in the primary storagesystem that has not been provided to a cloud service system and themetadata associated with content stored in the registered storagecluster that has not been provided to the cloud service system.

At 304, the received metadata is stored and indexed together. Inresponse to receiving from one or more registered storage clusters themetadata associated with a plurality of objects, the cloud servicesystem may perform an ETL process and consolidate a result of the ETLprocess in a global index.

At 306, a unified metadata search interface is provided. A UI servicevirtualization container may provide a user interface that includes theunified metadata search interface. The unified metadata search interfacemay enable a user associated with the enterprise to perform a globalsearch for any object stored in the plurality of different storagedomains. A user associated with the enterprise may use one or moremetadata attributes to search for any of the objects in the one or morestorage domains associated with the enterprise.

The cloud service system may generate a searchable index based on themetadata, however, the searchable index may become out-of-date becauseone or more objects in the primary storage system and/or the storagecluster may be subsequently deleted, modified, or added. To ensure thatthe searchable index is up-to-date within a threshold duration (e.g., 15minutes), the storage cluster may be configured to provide the metadataassociated with a plurality of objects stored in the primary storagesystem and the metadata associated with a plurality of objects stored inthe storage cluster according to an update policy.

The update policy may indicate that a storage cluster is configured toprovide to the cloud service system the metadata associated with aplurality of objects stored in the primary storage system and themetadata associated with a plurality of objects stored in the storagecluster on a periodic basis (e.g., every five minutes, every tenminutes, every fifteen minutes, etc.). The update policy may indicatethat an incremental set of metadata is to be provided to the cloudservice system after the initial set of metadata. The storage clustermay reduce the amount of bandwidth used to send the metadata to thecloud service system from the storage cluster by sending an incrementalset of metadata instead of sending the full set of metadata. Sending anincremental set of metadata may also reduce the overall amount of timeto keep the searchable index up-to-date because the cloud storage systemmay be processing less data to update the searchable index. The metadatato be included in the incremental set of metadata may be determinedbased on a timestamp associated with the metadata. For example, thestorage cluster may provide the metadata for objects having a timestamplater than a timestamp associated with a last update. In someembodiments, the update policy indicates that a storage cluster isconfigured to provide to the cloud service system the metadataassociated with a plurality of objects stored in the primary storagesystem and the metadata associated with a plurality of objects stored inthe storage cluster after a threshold amount of metadata has changed. Insome embodiments, the update policy indicates that a storage cluster isconfigured to provide to the cloud service system the metadataassociated with a plurality of objects stored in the primary storagesystem and the metadata associated with a plurality of objects stored inthe storage cluster in response to a command from a user associated withthe enterprise. In other embodiments, the update policy indicates that astorage cluster is configured to provide to the cloud service system themetadata associated with a plurality of objects stored in the primarystorage system and/or the metadata associated with a plurality ofobjects stored in the storage cluster any time the metadata associatedwith a plurality of objects stored in the primary storage system or themetadata associated with a plurality of objects stored in the storagecluster has changed.

FIG. 4 is a flow chart illustrating a process for performing a searchusing a unified metadata search interface in accordance with someembodiments. In the example shown, process 400 may be implemented by acloud service system, such as cloud service system 131. In someembodiments, process 400 is implemented to perform some or all of step306 of process 300.

At 402, a request for one or more objects based on one or more metadataattributes is received at a unified metadata search interface. A cloudservice system may store in an index metadata associated with aplurality objects stored in one or more storage domains. The cloudservice system may include a UI service virtualization container that isconfigured to provide a user interface. The user interface may includethe unified metadata search interface. A user interacting with theunified metadata search interface may provide a request for one or moreobjects based on one or more metadata attributes. The one or moremetadata attributes associated with an object may include, but are notlimited to, file name, network name, internet protocol (IP address), VMtype, application type, application name, operating system (OS) name, OStype, date backed up, file size, location (e.g., which system stores theobject), etc.

At 404, one or more indexed objects matching the one or more metadataattributes are determined. The cloud service system may use the index todetermine the one or more objects matching the one or more metadataattributes. The index may be up-to-date within a threshold duration(e.g., up-to-date since a last update). The cloud service system may beable to determine a corresponding storage domain associated with the oneor more objects matching the one or more metadata attributes. The cloudservice system may also be able to determine a location within thecorresponding storage domain associated with the one or more objectsmatching the one or more metadata attributes, i.e., whether an object isstored in a primary storage system of the corresponding storage domainor a storage cluster of the corresponding storage domain.

At 406, an indication of the one or more indexed objects satisfying therequest is provided. The cloud service system may provide via theunified metadata search interface a list of the one or more indexedobjects satisfying the request. In addition to the one or more requestedmetadata attributes, the list may also include one or more othermetadata attributes associated with the one or more objects matching therequested one or more metadata attributes. The indication may include acorresponding location associated with the one or more indexed objectssatisfying the request. The corresponding location may include a storagedomain of the different storage domains, a primary storage system of thestorage domain, or a storage cluster of the storage domain.

FIG. 5 is a flow chart illustrating a process for performing a backupjob in accordance with some embodiments. In the example shown, process500 may be implemented by a cloud service system, such as cloud servicesystem 131.

At 502, a central storage management interface for a plurality ofdifferent storage clusters included in different storage domains isprovided. A cloud service system may include a UI service virtualizationcontainer that is configured to provide a user interface that includes acentral storage management interface. The central storage managementinterface may include an overview screen that displays a list ofregistered storage clusters associated with a user. The overview screenmay provide information associated with each of the available storageclusters. For example, the information associated with an availablestorage cluster may include deduplication statistics associated with thestorage cluster (e.g., amount of data that is deduped, ratio of dedupeddata to non-deduped data, etc.), the last time a backup snapshot wasperformed by the storage cluster, a list of the most recent backup jobsperformed, the available amount of storage associated with the storagecluster, the amount of available processing resources associated withthe storage cluster, a protection policy associated with the storagecluster (e.g., gold, silver, bronze, etc.), and/or whether the storagecluster is online or offline.

A protection policy may indicate a set of available features associatedwith the storage cluster. A gold policy may indicate that all of thefeatures associated with the storage cluster are available. A silverpolicy may indicate that a first subset of the features associated withthe storage cluster are available. A bronze policy may indicate that asecond subset of the features associated with the storage cluster areavailable where the second subset of features is smaller than the firstsubset of features.

In some embodiments, the list of registered storage clusters includesall of the registered storage clusters associated with an enterprise. Inother embodiments, the list of registered storage clusters includes allof the registered storage clusters associated with a particular userID.

At 504, an indication of one of the plurality of different storageclusters is received. The UI service virtualization container of thecloud service system may receive a selection of one of the registeredstorage clusters from a user associated with an enterprise.

At 506, a native user interface version associated with the indicatedstorage cluster is provided. In response to the indication, the UIservice virtualization container may determine a version of a nativeuser interface associated with the indicated storage cluster and loadthe user interface code associated with the native user interfaceversion of the indicated storage cluster. The native user interface maybe accessed via a portion of the central storage management interface(e.g., inline frame). This may enable the user associated with theenterprise to interact with the central storage management interfaceassociated with the UI service virtualization container as if the userwere local to the user interface of the indicated storage cluster.

The one or more available protection jobs associated with the indicatedstorage cluster may be filtered based on the protection policyassociated with the indicated storage cluster. The one or more availableprotection jobs associated with the indicated storage cluster may befiltered based on whether the primary storage system associated with theindicated storage cluster is available or the indicated storage clusteris available.

At 508, one or more commands associated with the indicated storagecluster are received. A user associated with the enterprise may use thecentral storage management interface to cause the indicated storagecluster to perform one or more backup commands. In some embodiments, theone or more backup commands cause one or more objects associated with aprimary storage system associated with the indicated storage cluster tobe backed up to the indicated storage cluster. In other embodiments, theone or more backup commands cause one or more objects associated with aprimary storage system associated with the indicated storage cluster tobe backed up to one of the other registered storage clusters. In someembodiments, the one or more backup commands cause the primary storagesystem associated with the indicated storage cluster to perform a backupsnapshot (full or incremental) to the indicated storage cluster. In someembodiments, the one or more backup commands cause the primary storagesystem associated with the indicated storage cluster to perform a backupsnapshot (full or incremental) to one of the other registered storageclusters. In some embodiments, the one or more backup commands cause theindicated storage cluster to restore one or more objects stored on theindicated storage cluster to the primary storage system associated withthe indicated storage cluster. In some embodiments, the one or morebackup commands cause the indicated storage cluster to restore one ormore objects stored on the indicated storage cluster to a primarystorage system associated with one of the primary storage systemsassociated with one of the other registered storage clusters. In someembodiments, the one or more backup commands cause the indicated storagecluster to archive one or more objects stored on the indicated storagecluster to a cloud archive. In some embodiments, the one or more backupcommands cause the indicated storage cluster to retrieve one or moreobjects stored in the cloud archive to the indicated storage cluster.

At 510, the one or more commands are provided to the indicated storagecluster. In response to receiving the one or more commands, the UIservice virtualization container may be configured to request from acaching service virtualization container of the cloud service system anidentifier associated with a persistent connection virtualizationcontainer corresponding to the indicated storage cluster. A cachingservice virtualization container may respond to the request byinspecting (e.g., a lookup) a data structure stored by caching servicevirtualization container to identify a persistent connectionvirtualization container associated with the indicated storage cluster.For example, the caching service virtualization container may determinean IP address of a persistent connection virtualization container thatis associated with the indicated storage cluster. The caching servicevirtualization container may then provide the UI service virtualizationcontainer the identifier (e.g., IP address) associated with thepersistent connection virtualization container corresponding to theindicated storage cluster. The UI service virtualization container mayprovide the one or more commands to the persistent connectionvirtualization container associated with the indicated storage clusterhaving the identifier. The persistent connection virtualizationcontainer associated with the indicated storage cluster may then forwardthe one or more commands to the indicated storage cluster, which inresponse to receiving the one or more commands, is configured to performone or more backup jobs based on the one or more commands.

FIG. 6 is a block diagram illustrating a central storage managementinterface in accordance with some embodiments. In the example shown,central storage management interface 600 may be provided by a UI servicevirtualization container, such as UI service virtualization container134.

A UI service virtualization container may be configured to providecentral storage management interface 600. Central storage managementinterface 600 may provide an overview screen (not shown) that displays alist of available storage clusters. The UI service virtualizationcontainer may receive an indication of a storage cluster via centralstorage management interface.

In response to the selection, the UI service virtualization containermay determine a version of a native user interface associated with theindicated storage cluster by inspecting a data structure that storesconfiguration information associated with a plurality of registeredstorage clusters. The configuration information may include the nativeuser interface version associated with a registered storage cluster. Thenative user interface version associated with the registered secondarystorage may be associated with a particular user interface code. A cloudservice system associated with the UI service virtualization containermay store a copy of the user interface code corresponding to differentnative user interface versions of a storage cluster.

The UI service virtualization container may load the user interface codeassociated with the indicated storage cluster. The native user interfacemay be accessed via portion 602 of central storage management interface600. The first portion 602 of central storage management interface 600may be an inline frame (iframe). The second portion 604 of userinterface 600 may be a header that is displayed regardless of whichstorage cluster is indicated. In some embodiments, a name of theindicated storage cluster is displayed in the second portion 604.

FIG. 7 is a flow chart illustrating a process for providing a userinterface in accordance with some embodiments. In the example shown,process 700 may be implemented by a UI service virtualization container,such as UI service virtualization container 134. Process 700 may beimplemented to perform some or all of step 506 of process 500.

At 702, a version of a native user interface associated with anindicated storage cluster is determined. A UI service virtualizationcontainer of a cloud service system may be configured to provide a userinterface that includes a central storage management interface. Thecentral storage management interface may provide an overview screen anddisplay a list of available storage clusters. The UI servicevirtualization container may receive an indication of a storage clustervia the central storage management interface.

Each of the storage clusters may be registered by a user. During acluster registration procedure, a storage cluster may provideconfiguration information to the cloud service system. The configurationinformation may indicate a version of a native user interface associatedwith the storage cluster. Each native user interface version isassociated with a particular user interface code. The cloud servicesystem may store a data structure that associates a storage cluster witha native user interface version, and a particular user interface code.The cloud service system may be configured to store a copy of the userinterface code associated with the different native user interfaceversions. The cloud service system may inspect the data structure todetermine the version of the native user interface associated with theindicated storage cluster.

At 704, the native user interface version is loaded. The native userinterface version may be loaded to provide a remote native managementinterface of the indicated storage cluster within a user interfacecontext of the central storage management interface. User interface codeassociated with the determined native user interface version of theindicated storage cluster is loaded and the native user interface may beaccessed via a portion of the central storage management interface. Thecentral storage management interface may include an iframe. The userinterface code associated with the determined native user interfaceversion of the indicated storage cluster may be accessed via the iframe.This may enable the user to interact with the central storage managementinterface associated with the cloud service system as if the user werelocal to the user interface of the indicated storage cluster. This mayalso reduce any user interface confusion the user may encounter.

FIG. 8 is a flow chart illustrating a process for performing a backupjob in accordance with some embodiments. In the example shown, process800 may be implemented by a cloud service system, such as cloud servicesystem 131. Process 800 may be implemented to perform some or all of 510of process 500.

At 802, one or more commands for an indicated storage cluster arereceived at a central storage management interface associated with acloud service system. An indicated storage cluster may have anassociated identifier. When the indicated storage cluster is registeredwith the cloud service system, the cloud service system may store a datastructure that associates the storage cluster with a storage clusteridentifier, a persistent connection virtualization container, andconfiguration information associated with the storage clusteridentifier. The configuration information may indicate a version of anative user interface associated with the storage cluster.

A UI service virtualization container may provide a user interface tothe user device. The user interface may be a unified managementinterface for all of the storage clusters to which a user is associated.The unified management interface may enable the user to remotely accessand manage storage clusters that are physically located separatelythroughout the world from a single location. The unified managementinterface may be comprised of a unified metadata search interface and acentral storage management interface. For example, the user may use theunified metadata search interface to search for any object stored in oneor more storage domains. The user may use the central storage managementinterface to send one or more commands to at least one of the storageclusters via the user interface provided by the UI servicevirtualization container. For example, a user associated with thestorage cluster may at any time request via the central storagemanagement interface associated with the cloud service system, for thestorage cluster of the storage domain to perform a backup snapshot ofthe file system data associated with the primary storage system of thestorage domain.

The UI service virtualization container does not know which persistentconnection virtualization container of the plurality of persistentconnection virtualization containers is to receive the one or morecommands because it does not store such information.

At 804, an identifier associated with a persistent connectionvirtualization container corresponding to the indicated storage clusteris requested. The UI service virtualization container may provide astorage cluster identifier associated with the indicated storage clusterto a caching service virtualization container. The caching servicevirtualization container may respond to the request by inspecting a datastructure stored by the caching service virtualization container toidentify a persistent connection virtualization container associatedwith the specified storage cluster identifier. The caching servicevirtualization container may respond to the request by providing the UIservice virtualization container the identifier (e.g., IP address)associated with the persistent connection virtualization containercorresponding to the indicated storage cluster.

At 806, the identifier associated with a persistent connectionvirtualization container corresponding to the indicated storage clusteris received.

At 808, the one or more commands are provided to the persistentconnection virtualization container associated with the indicatedstorage cluster. The one or more commands are provided to the persistentconnection virtualization container having the identifier received fromthe caching service virtualization container. In response to receivingthe one or more commands, the persistent connection virtualizationcontainer is configured to provide the one or more commands to theindicated storage cluster. In response to receiving the one or morecommands, the indicated storage cluster is configured to perform one ormore secondary storage functions (e.g., a backup, a restore, etc.) basedon the one or more commands.

FIG. 9 is a diagram illustrating a system for registering a storagecluster in accordance with some embodiments. In the example shown,system 900 includes browser 902, storage cluster 904, cloud identityprovider 906, and cloud service system 908. Storage cluster 904 may beimplemented by a storage cluster, such as storage cluster 104, 114, 124,204. Cloud service system 908 may be implemented by a cloud servicesystem, such as cloud service system 131.

Browser 902 is associated with a user device. The user device may be acomputer, a laptop, a desktop, a server, a mobile device, a smartphone,a cellular phone, a smart watch, a tablet, a personal data assistant, orany other electronic device capable of running a web browser. Browser902 may be any web browser capable of browsing the Internet (e.g.,Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, AppleSafari, etc.). Browser 902 may enable a user associated with storagecluster 904 to remotely access and manage storage cluster 904.

Storage cluster 904 may be part of a storage domain that is comprised ofa primary system and a storage cluster. The primary system may becomprised of an object, virtual machine, physical entity, file system,array backup, and/or volume that stores file system data. Storagecluster 904 may cause the primary system to perform a backup snapshotaccording to a backup policy and to store the backup snapshot to storagecluster 904. A backup snapshot represents the state of the primarysystem at a particular point in time (e.g., the state of the file systemdata). The backup policy may require a full backup snapshot and/or anincremental backup snapshot to be performed. A full backup snapshotstores the entire state of the primary system at a particular point intime. The file system data is comprised of a plurality of data blocks.The primary system may include a change block tracker that monitors andidentifies one or more data blocks of the primary system that havechanged (e.g., modified, deleted, added) since the last backup snapshot.An incremental backup snapshot includes the one or more data blocks thathave changed since the last backup snapshot.

A user associated with storage cluster 904 may be permitted to accessand manage the one or more backup snapshots stored in storage cluster904. For example, a user associated with storage cluster 904 may bepermitted to restore the primary system to a state associated with oneof the backup snapshots stored in storage cluster 904. A user associatedwith storage cluster 904 may be permitted to restore to the primarysystem a file associated with one of the backup snapshots stored instorage cluster 904. A user associated with the storage cluster 904 maybe permitted to cause the primary system associated with storage cluster904 to perform a backup snapshot. A user associated with storage cluster904 may delete one of the backup snapshots that is stored on storagecluster 904.

In some embodiments, the user associated with storage cluster 904 isassociated with a second storage cluster. The user associated withstorage cluster 904 may be permitted to restore the primary systemassociated with the storage cluster using one of the backup snapshotsstored in storage cluster 904. The user associated with storage cluster904 may be permitted to restore the primary system associated withstorage cluster 904 using one of the backup snapshots associated withthe storage cluster.

A user associated with storage cluster 904 may remotely access andmanage storage cluster 904. For example, a user associated with storagecluster 904 may remotely log into storage cluster 904 via a VPNconnection. However, the user associated with storage cluster 904 may beassociated with a plurality of storage clusters. For example, anenterprise may have storage domains that include corresponding storageclusters located throughout the world for various reasons. To access andmanage each of the storage clusters may require the user to maintainseparate connections for each of the storage clusters.

To reduce the number of browser sessions, a user associated with storagecluster 904 may register storage cluster 904 with cloud service system908. The user associated with storage cluster 904 may also register oneor more other storage clusters with cloud service system 908. Thisenables the user to access and manage the storage clusters from a singleunified interface.

Storage cluster 904 may be located a firewall. As a result, cloudservice system 908 cannot directly initiate a connection with storagecluster 904. However, storage cluster 904 may initiate a process toconnect with cloud service system 908.

A user associated with storage cluster 904 via browser 902 may enablestorage cluster 904 to communicate with cloud service system 908 andinitiate a cluster registration procedure. The user may log into storagecluster 904 using an internet protocol (IP) address associated withstorage cluster 904 or a virtual IP (VIP) address associated with one ofthe nodes of the storage cluster 904. In response to the user enablingstorage cluster 904 to communicate with cloud service system 908 andinitiating the cluster registration procedure, storage cluster 904 maygenerate cluster state information (e.g., a cluster identifier, acluster incarnation identifier, the name of a cluster, a security token,and/or a name of a host) that allows cloud service system 908 toregister storage cluster 904. The security token may include a nonce, aone-time password, a reusable password, etc. The name of the hostcorresponds to the manner in which the user logged into storage cluster904. For example, the name of the host may correspond to a VIP addressassociated with one of the nodes of storage cluster 904 in the event auser logged into storage cluster 904 using a VIP address associated withone of the storage cluster nodes. The name of the host may correspond toan IP address associated with one of the nodes of storage cluster 904 inthe event a user logged into storage cluster 904 using an IP addressassociated with one of the storage cluster nodes. The cluster stateinformation enables cloud service system 908 to identify storage cluster904. The cluster state information may be generated by one of thestorage cluster nodes and may be propagated to the other nodes ofstorage cluster 904. This allows any of the storage cluster nodes tofinish a cluster registration procedure when directed by cloud servicesystem 908.

Storage cluster 904 is configured to provide the cluster stateinformation to browser 902 and to cause browser 902 to be redirected tocloud identity provider 906. The redirection may include cluster stateinformation associated with storage cluster 904. For example, thecluster state information may include the cluster identifier,configuration information (e.g., native interface version information),the cluster incarnation identifier, the name of a cluster, the securitytoken (e.g., nonce, a one-time password, reusable password, etc.),and/or the name of a host. The cluster state information included in theredirect may be encrypted using a shared secret that is shared betweenstorage cluster 904 and cloud service system 908

Cloud identity provider 906 (e.g., Salesforce) may be an identityprovider for a cloud service. Cloud identity provider 906 may store adata structure that maps a user account with one or more storageclusters. Cloud identity provider 906 may request the user to providevia browser 902 authentication information associated with the user. Forexample, the user may provide account information associated with cloudidentity provider 906, such as a username and password. The datastructure associated with cloud identity provider 906 may associate thereceived account information with one or more storage clusters. The userassociated with browser 902 may only access the one or more storageclusters that are associated with the received account information.

Upon successful authentication, cloud identity provider 906 may redirectbrowser 902 to cloud service system 908. The redirection may include thecluster state information and a code. Browser 902 is configured toprovide the cluster state information and the code to cloud servicesystem 908. The cluster state information may be encrypted. Cloudservice system 908 may decrypt the encrypted cluster state informationusing the shared secret. Cloud service system is configured to store thecluster state information. Cloud service system 908 may be configured tostore the cluster state information for a predetermined period of time(e.g., 15 minutes). In the event a connection is not established betweencloud service system 908 and storage cluster 904, cloud service system908 is configured to delete the cluster state information. In the eventcloud service system 908 is unable to decrypt the encrypted clusterstate information, cloud service system 908 may terminate the clusterregistration procedure. This indicates that the cluster registrationprocedure was not initiated by a valid storage cluster.

Cloud service system 908 is configured to provide the code to cloudidentity provider 906 and to request an access token from the cloudidentity provider 906. The cloud identity provider may validate the codeby comparing the code with the code provided in the browser redirect.The code is validated in the event the code received from the cloudservice system matches the code provided in the browser redirect. Uponvalidating the code, cloud identity provider 906 is configured toprovide the access token to cloud service system 908. In response toreceiving the access token, cloud service system 908 is configured torequest user information based on one or more parameters. The parametermay be the access token. Cloud identity provider 906 is configured toprovide user information to cloud service system 908. The userinformation includes account information associated with theauthentication information provided by the user. The account informationmay indicate the one or more storage clusters associated with a user.Cloud service system 908 may be configured to verify that the userinformation matches the cluster state information. For example, cloudservice system 908 may be configured to verify that a cluster identifierincluded in the user information matches the cluster identifier includedin the cluster state information. In the event the user information doesnot match the cluster state information, cloud service system 908 isconfigured to terminate the cluster registration procedure. In the eventthe user information matches the cluster state information, cloudservice system 908 is configured to redirect browser 902 to the clusterhaving the host name included in the cluster state information. Browser902 may be redirected to a node of storage cluster 904 based on themanner in which the user logged into storage cluster 904. For example,browser 902 is redirected to a VIP address associated with a storagecluster node in the event the user logged into the storage cluster usingthe VIP address associated with a storage cluster node. In otherembodiments, browser 902 is redirected to an IP address associated witha storage cluster node in the event the user logged into storage cluster904 using the IP address associated with the storage cluster node.

The redirect may cause the storage cluster to which browser 104 isdirected to finish the cluster registration procedure. The clusterregistration procedure may be finished by any of the nodes of storagecluster 904 even though the host name is associated with one of thestorage cluster nodes because the cluster state information has beensynced to all of the storage cluster nodes. The storage cluster nodehandling the redirect may request a certificate from cloud servicesystem 908 and provide the cluster state information to the cloudservice system 908. The cluster state information may be encrypted.Cloud service system 908 may compare the instance of the security tokenincluded in the cluster state information received from storage cluster904 to the instance of the security token included in the cluster stateinformation received from browser 902 via the cloud identity provider906 redirect.

In the event the second instance of the security token matches the firstinstance of the security token, cloud service system 908 is configuredto provide a certificate to storage cluster 904. The certificate mayenable storage cluster 904 to communicate with cloud service system 908.In some embodiments, the instance of the security token received fromthe cloud identity provider 906 via browser 902 is valid for apredetermined duration (e.g., 15 mins). In the event cloud servicesystem 908 does not receive a security token from a storage cluster thatmatches the security token received from cloud identity provider 906 viabrowser 902 within the predetermined duration, cloud service system 908is configured to deny a cluster registration. The storage cluster isconfigured to store the certificate.

The certificate is signed by cloud service system 908. The certificatemay be provided back to cloud service system 908 to allow cloud servicesystem 908 to verify that storage cluster 904 can be trusted because itpossesses a certificate that was signed by cloud service system 908. Inthe event the instance of the security token received from storagecluster 904 does not match the instance of the security token receivedfrom cloud identity provider 906 via browser 902, cloud service system908 does not provide a certificate to storage cluster 904 and aconnection cannot be established between the storage cluster 904 andcloud service system 908. Upon receiving the certificate, storagecluster 904 is configured to store the certificate. Storage cluster 904includes a distributed store and the received certificate is stored inthe distributed store. Storage cluster 904 is comprised of a masterstorage node and a plurality of secondary storage nodes. In the eventthe master storage node is offline, one of the remaining storage nodesmay re-establish communications with cloud service system 908 using thecertificate that is stored in the distributed store.

In response to receiving the certificate, storage cluster 904 isconfigured to redirect browser 902 to the initial login page, to providea notification indicating that the cluster registration procedure wassuccessful, and to establish bidirectional communications betweenstorage cluster 904 and cloud service system 908. The notificationindicates that the cluster registration procedure was successful, i.e.,storage cluster 904 is registered with cloud service system 908. In theevent the cluster registration procedure is successful, the user mayaccess storage cluster 904 via cloud service system 908 without havingto establish a VPN connection with storage cluster 904. The user mayperform the same procedure for a plurality of other storage clusters.Subsequently, the user may manage the one or more storage clusters via asingle browser session. After the user registers a storage cluster, thestorage cluster may be configured to provide cloud service system 908the metadata associated with a plurality of objects stored in theprimary storage system associated with a registered storage cluster andthe metadata associated with a plurality of objects stored in theregistered storage cluster. Cloud service system 908 may provide aunified metadata interface that allows a user to perform a global searchbased on metadata attributes associated with a plurality of objectsstored in storage domains associated with the user.

FIG. 10 is an example of a process for registering a storage cluster inaccordance with some embodiments. In the example shown, process 1000 maybe performed by a system for registering a storage cluster, such assystem 900.

At 1002, login information is received at a storage cluster from a uservia a browser. The user may log into the storage cluster using aninternet protocol (IP) address associated with the storage cluster or avirtual IP (VIP) address associated with one of the nodes of the storagecluster.

In response to a successful login, the storage cluster may provide auser interface that allows the user to enable a cluster registration. Acluster registration procedure is a procedure that enables a user toaccess and manage one or more storage cluster via a cloud servicesystem. A user may enable a cluster registration procedure via thebrowser associated with the user device.

A user associated with the storage cluster may be associated with aplurality of storage clusters. The storage clusters may be remote fromeach other. Instead of establishing a separate browser session with eachstorage cluster to manage each storage cluster, the user may desire tointeract with the plurality of storage cluster using a single browsersession.

At 1004, the storage cluster generates the cluster state information inresponse to the user enabling the cluster registration. The clusterstate information may include a cluster identifier, configurationinformation (e.g., native interface version information), a clusterincarnation identifier, a name of a cluster, a security token (e.g.,nonce, a one-time password, reusable password, etc.), and/or a name of ahost. The name of the host corresponds to the manner in which the userlogged into the storage cluster. For example, the name of the host maycorrespond to a VIP address associated with one of the nodes of thestorage cluster in the event a user logged into the storage clusterusing a VIP address associated with one of the storage cluster nodes.The name of the host may correspond to an IP address associated with oneof the nodes of the storage cluster in the event a user logged into thestorage cluster using an IP address associated with one of the storagecluster nodes. A storage node of the storage cluster is configured togenerate the cluster state information and to propagate the generatedcluster state information to the other nodes of the storage cluster.This enables any of the storage cluster nodes to complete the clusterregistration procedure when directed by a cloud service system. Thecluster state information allows the cloud service system to identify astorage cluster that is requesting a cluster registration to beestablished.

At 1006, cluster state information is provided from the storage clusterto the browser associated with a user and the browser associated withthe user is redirected to a cloud identity provider. In someembodiments, the provided cluster state information is encrypted using ashared secret that is shared between a storage cluster and a cloudservice system. This prevents non-authorized users from attempting toregister the storage cluster.

At 1008, the cloud identity provider requests the user to provideauthentication information via the browser. For example, the user mayprovide account information associated with the cloud identity provider,such as a username and password. The user logs into the cloud identityprovider and the browser associated with the user provides the clusterstate information to the cloud identity provider. The accountinformation associated with the cloud identity provider may beassociated with one or more storage clusters. A user may only access theone or more storage clusters to which the account information associatedwith the cloud identity provider is associated.

At 1010, the cloud identity provider authenticates the user andredirects the browser associated with the user to a cloud servicesystem. The redirect includes the cluster state information and a code.

At 1012, the browser associated with the user provides the cluster stateinformation and the code to the cloud service system. The cluster stateinformation may be encrypted. The cloud service system may decrypt theencrypted cluster state information using the shared secret. The cloudservice system is configured to store the cluster state information. Inthe event the cloud service system is unable to decrypt the encryptedcluster state information, the cloud service system may terminate thecluster registration procedure. This indicates that the clusterregistration procedure was not initiated by a valid storage cluster.

At 1014, the cloud service system provides the code to the cloudidentity provider and requests an access token from the cloud identityprovider.

At 1016, in response to validating the code, the cloud identity providerprovides the access token to the cloud service system. At 1018, inresponse to receiving the access token, the cloud service systemrequests user information based on one or more parameters. The parametermay be the access token. At 1020, the cloud identity provider providesuser information to the cloud service system. The user informationincludes account information associated with the authenticationinformation provided by the user. The account information may indicatethe one or more storage clusters associated with a user.

At 1022, the cloud service system is configured to verify that the userinformation matches the cluster state information. For example, thecloud service system may be configured to verify that a clusteridentifier included in the user information matches the clusteridentifier included in the cluster state information. In the event theuser information does not match the cluster state information, the cloudservice system is configured to terminate the cluster registrationprocedure. In the event the user information matches the cluster stateinformation, the cloud service system is configured to redirect thebrowser associated with the user to the cluster having the host nameincluded in the cluster state information.

At 1024, the browser associated with the user is redirected to a node ofthe storage cluster based on the manner in which the user logged intothe storage cluster. For example, the browser associated with the useris redirected to a VIP address associated with a storage cluster node inthe event the user logged into the storage cluster using the VIP addressassociated with a storage cluster node. In other embodiments, thebrowser associated with the user is redirected to an IP addressassociated with a storage cluster node in the event the user logged intothe storage cluster using the IP address associated with the storagecluster node.

At 1026, the redirect may cause the storage cluster to which the browseris directed to finish the cluster registration procedure. The clusterregistration procedure may be finished by any of the nodes of thestorage cluster even though the host name is associated with one of thestorage cluster nodes because the cluster state information has beensynced to all of the storage cluster. The storage cluster node handlingthe redirect may request a certificate from the cloud service system andprovide the cluster state information to the cloud service system. Thecluster state information may be encrypted.

At 1028, the cloud service system is configured to validate the storagecluster at least in part by comparing the second instance of thesecurity token included in the cluster state information received fromthe storage cluster to the first instance of the security token includedin the cluster state information received from the browser via the cloudidentity provider redirect. In the event the second instance of thesecurity token matches the first instance of the security token, thecloud service system is configured to provide a certificate to thestorage cluster. The certificate may enable the storage cluster tocommunicate with the cloud service system. In some embodiments, theinstance of the security token received from the cloud identity provideris valid for a predetermined duration (e.g., 15 mins). In the event thecloud service system does not receive a security token from a storagecluster that matches the security token received from the cloud identityprovider within the predetermined duration, the cloud service system isconfigured to deny a cluster registration.

At 1030, the storage cluster is configured to store the certificate. Thestorage cluster includes a distributed store and the receivedcertificate is stored in the distributed store. The storage cluster iscomprised of a master storage node and a plurality of secondary storagenodes. In the event the master storage node is offline, one of theremaining storage nodes may re-establish communications with the cloudservice system using the certificate that is stored in the distributedstore.

At 1032, the storage cluster is configured to redirect the browser tothe initial login page, to provide a notification indicating that thecluster registration procedure was successful, and to establishbidirectional communications between the storage cluster and the cloudservice system.

In the event the cluster registration procedure is successful, the usermay access and manage the storage cluster via the cloud service systemwithout having to establish a VPN connection with the storage cluster.The user may perform the same procedure for a plurality of other storageclusters. Subsequently, the user may manage the plurality of storageclusters via a single browser session. After the user registers astorage cluster, the storage cluster may be configured to provide acloud service system the metadata associated with a plurality of objectsstored in the primary storage system associated with a registeredstorage cluster and the metadata associated with a plurality of objectsstored in the registered storage cluster. A cloud service system mayprovide a unified metadata interface that allows a user to perform aglobal search based on metadata attributes associated with a pluralityof objects stored in storage domains associated with the user.

FIG. 11 is a diagram illustrating a timeline for registering a storagecluster in accordance with some embodiments. In the example shown,timeline 1100 may be implemented by a system for registering a storagecluster, such as system 900.

Browser 902 logs into storage cluster 904. A user associated withbrowser 902 may log into storage cluster 904 using an internet protocol(IP) address associated with the storage cluster or a virtual IP (VIP)address associated with one of the nodes of the storage cluster. Inresponse to a successful login, storage cluster 904 may provide a userinterface that allows a user associated with browser 902 to enable acluster registration procedure.

Storage cluster 904 is configured to generate cluster state informationin response to the user enabling the cluster registration procedure. Thecluster state information may include a cluster identifier,configuration information (e.g., native interface version information),a cluster incarnation identifier, a name of a cluster, a security token(e.g., nonce, a one-time password, reusable password, etc.), and/or aname of a host. The cluster state information allows cloud servicesystem 908 to identify a storage cluster of a storage domain that isrequesting a cluster registration to be established. The name of thehost corresponds to the manner in which the user logged into the storagecluster. For example, the name of the host may correspond to a VIPaddress associated with one of the nodes of the storage cluster in theevent a user logged into the storage cluster using a VIP addressassociated with one of the storage cluster nodes. The name of the hostmay correspond to an IP address associated with the storage cluster inthe event a user logged into the storage cluster using an IP addressassociated with the storage cluster. The cluster state information maybe generated by one of the storage cluster nodes and propagated to theother nodes of the storage cluster. This allows any of the storagecluster nodes to finish a cluster registration procedure when directedby the cloud service system.

Storage cluster 904 provides the cluster state information to browser902 and browser 902 is redirected to a cloud identity provider 906. Thecluster state information may be encrypted using a shared secret that isshared between storage cluster 904 and cloud service system 908. Cloudidentity provider 906 requests the user to provide authenticationinformation via the browser 902. For example, the user may provideaccount information associated with cloud identity provider 906, such asa username and password.

The user logs into cloud identity provider 906 and browser 902 providesthe cluster state information to cloud identity provider 906. Theaccount information associated with the cloud identity provider may beassociated with one or more storage cluster. A user may only access theone or more storage clusters to which the account information associatedwith the cloud identity provider is associated.

Cloud identity provider 906 authenticates the user. For example, theuser may provide account information associated with the cloud identityprovider, such as a username and password. The account informationassociated with the cloud identity provider may be associated with oneor more storage cluster. A user may only access the one or more storagecluster to which the account information is associated.

Cloud identity provider 906 redirects browser 902 to cloud servicesystem 908. The redirect includes the cluster state information and acode.

Browser 902 provides the cluster state information and the code to cloudservice system 908. The cluster state information may be encrypted. Thecloud service system may decrypt the encrypted cluster state informationusing the shared secret. The cloud service system is configured to storethe cluster state information. In the event the cloud service system isunable to decrypt the encrypted cluster state information, the cloudservice system may terminate the cluster registration procedure. Thisindicates that the cluster registration procedure was not initiated by avalid storage cluster.

Cloud service system 908 provides the code to cloud identity provider906 and to request an access token from cloud identity provider 906.Cloud identity provider 906 may validate the code by comparing the codewith the code provided in the browser redirect. The code is validated inthe event the code received from cloud service system 908 matches thecode provided in the browser 902 redirect.

Upon validating the code, cloud identity provider 906 provides theaccess token to cloud service system 908.

In response to receiving the access token, cloud service system 908 isconfigured to request user information based on one or more parameters.The parameter may be the access token.

Cloud identity provider 108 is configured to provide user information tocloud service system 908. The user information includes accountinformation associated with the authentication information provided bythe user. The account information may indicate the one or more storageclusters associated with a user.

Cloud service system 908 verifies that the user information matches thecluster state information. For example, the cloud service system may beconfigured to verify that a cluster identifier included in the userinformation matches the cluster identifier included in the cluster stateinformation. In the event the user information does not match thecluster state information, cloud service system 908 is configured toterminate the cluster registration procedure. In the event the userinformation matches the cluster state information, cloud service system908 is configured to redirect the browser 108 to the storage clusterhaving the host name included in the cluster state information.

Browser 902 is redirected to a node of storage cluster 904 based on themanner in which the user logged into storage cluster 904. For example,the browser associated with the user is redirected to a VIP addressassociated with a storage cluster node in the event the user logged intostorage cluster 904 using the VIP address associated with a storagecluster node. In other embodiments, browser 902 is redirected to an IPaddress associated with a storage cluster node in the event the userlogged into storage cluster 904 using the IP address associated with thestorage cluster node.

The redirect causes storage cluster 904 to finish the clusterregistration procedure. The cluster registration procedure may befinished by any of the nodes of the storage cluster even though the hostname is associated with one of the storage cluster nodes because thecluster state information has been synced to all of the storage clusternodes.

The storage cluster node of storage cluster 904 handling the redirectmay request a certificate from cloud service system 908 and provide thecluster state information to the cloud service system 908. The clusterstate information may be encrypted. The cloud service system may comparethe second instance of the security token included in the cluster stateinformation received from the storage cluster to the first instance ofthe security token included in the cluster state information receivedfrom the browser via the cloud identity provider redirect.

In the event the second instance of the security token matches the firstinstance of the security token, cloud service system 908 is configuredto provide a certificate to storage cluster. The certificate may enablestorage cluster 904 to communicate with cloud service system 908. Insome embodiments, the instance of the security token received frombrowser 902 via cloud identity provider 906 is valid for a predeterminedduration (e.g., 15 mins). In the event cloud service system 908 does notreceive a security token from a storage cluster that matches thesecurity token received from the cloud identity provider within thepredetermined duration, the cloud service system is configured to deny acluster registration. Storage cluster 904 stores the certificate.

In response to receiving the certificate, the storage cluster isconfigured to redirect browser 902 to the initial login page, to providea notification indicating that the cluster registration procedure wassuccessful, and to establish bidirectional communications betweenstorage cluster 904 and cloud service system 908. In the event thecluster registration is successful, the user may access the storagecluster via the cloud service system without having to establish a VPNconnection with the cluster. The user may perform the same procedure fora plurality of other storage clusters. Subsequently, the user may managethe one or more storage clusters via a single browser session. After theuser registers a storage cluster, the storage cluster may be configuredto provide a cloud service system the metadata associated with aplurality of objects stored in the primary storage system associatedwith a registered storage cluster and the metadata associated with aplurality of objects stored in the registered storage cluster. The cloudservice system may provide a unified metadata interface that allows auser to perform a global search based on metadata attributes associatedwith a plurality of objects stored in storage domains associated withthe user.

FIG. 12 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1200 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1200 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1200 includes a unified metadatasearch interface 1202. Unified metadata search interface 1202 mayreceive a request for one or more objects associated with one or moreregistered storage clusters (including objects stored in a registeredstorage cluster or objects stored in a primary storage system associatedwith a registered storage cluster). The request may include one or moremetadata attributes associated with an object. The one or more metadataattributes associated with an object may include, but are not limitedto, file name, network name, internet protocol (IP address), VM type,application type, application name, operating system (OS) name, OS type,date backed up, file size, location (e.g., which system stores theobject), etc.

In the example shown, seven storage clusters associated with anenterprise have been registered. A user associated with the enterprisemay search for one or more objects via unified metadata search interface1202, using one or more metadata attributes associated with the object.In the example shown, a request for one or more objects with a metadataattribute of “test” has been entered into unified metadata searchinterface 1202.

User interface 1200 may provide other information associated with one ormore registered storage clusters. For example, user interface 1200 mayinclude protection run information, health information, storagereduction information, deduplication information, protectioninformation, protected object information, throughput information,recovery information, audit log information, input/output operations persecond (IOPS) information, etc.

FIG. 13 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1300 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1300 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1300 is displaying a plurality ofsearch results that match a request for one or more objects having ametadata attribute of “test.” User interface 1300 may be configured toprovide a preview pane 1304 for a selected search result 1302. Thepreview pane may be configured to display the one or more metadataattributes associated with a selected search result. The one or moredisplayed metadata attributes may be specific to the selected searchresult.

In the example shown, preview pane 1304 is displaying metadataattributes associated with the selected search result 1302 “testVolume.”For the object “testVolume,” preview pane 1304 is displaying metadataattribute information of “type,” “NAS,” “Clusters” (e.g., the storageclusters in which the object “testVolume” is stored), a location of abackup snapshot associated with the object, a number of backup snapshotsperformed, and when the last backup snapshot was performed.

FIG. 14 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1400 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1400 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1400 is displaying a plurality ofsearch results that match a request for one or more objects having ametadata attribute of “test.” User interface 1400 may be configured toprovide a preview pane 1404 for a selected search result 1402. Thepreview pane may be configured to display the one or more metadataattributes associated with a selected search result. The one or moredisplayed metadata attributes may be specific to the selected searchresult.

In the example shown, preview pane 1304 is displaying metadataattributes associated with the selected search result 1402 “nano-2.” Theobject “nano-2” is associated with a “Job:test.” For the object“nano-2,” preview pane 1404 is displaying metadata attribute informationof “type,” “SCVMM Server,” “Hypervisor,” “Clusters” (e.g., the storageclusters in which the object “nano-2” is stored), job summaryinformation, a location of two different backup snapshots associatedwith the object, a number of backup snapshots performed at eachlocation, and when the last backup snapshot was performed at eachlocation.

FIG. 15 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1500 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1500 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1500 is displaying a plurality offiltered search results that match a request for one or more objectshaving a metadata attribute of “test.” The one or more provided searchresults may be filtered based on “type,” “status,” and “last run.” Inthe example shown, user interface 1500 is displaying objects having ametadata attribute of “test” and have a status 1502 of “protected.”

FIG. 16 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1600 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1600 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1600 is displaying a plurality offiltered search results that match a request for one or more objectshaving a metadata attribute of “test.” The one or more provided searchresults may be filtered based on “type,” “status,” and “last run.” Inthe example shown, user interface 1600 is displaying objects having ametadata attribute of “test” and have a status 1602 of “unprotected.”

FIG. 17 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1700 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1700 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1700 is configured to provide acentral storage management interface for a plurality of registeredstorage clusters. User interface 1700 includes a drop down menu 1702that lists a plurality of registered storage clusters. In the exampleshown, the storage clusters having cluster names “democluster,”“tme-cluster-02,” “edison,” “cohesity-vSANReady,” “einstein,” “everest,”and “BirCluster” have been registered with a cloud service system, suchas cloud service system 131. In other embodiments, the storage clustersare registered with a master storage cluster. A registered storagecluster may be displayed in drop down menu 1702 even though theregistered storage cluster is offline (e.g., “democluster” is offline).In the example shown, user interface 1700 has received an indication(e.g., selection) for the storage cluster with the cluster name“everest.” In response to the indication, the cloud service system isconfigured to may be configured to determine a version of a native userinterface associated with the storage cluster with the cluster name“everest” and load the determined native user interface version. Theloaded native user interface version may be accessed via a portion ofuser interface 1700.

FIG. 18 is an example of a user interface in accordance with someembodiments. In the example shown, user interface 1800 may be providedby a cloud service system, such as cloud service system 131. In someembodiments, user interface 1800 is provided by a master storagecluster, such as storage cluster 104, storage cluster 114, or storagecluster 124.

In the example shown, user interface 1800 is configured to displaycluster information associated with one or more registered storageclusters. The cluster information may be provided to the cloud servicesystem when a storage cluster is registered with the cloud servicesystem. The cluster information may include a cluster name, a clusterID, a type, the number of nodes associated with the storage cluster, astorage capacity of the storage cluster, a health indicator associatedwith the storage cluster, a connection indicator associated with thestorage cluster, and version information associated with the storagecluster. The version information associated with the storage cluster maycorrespond to a version of a native user interface associated with thestorage cluster. For example, a storage cluster associated with aversion of “6.2” may have a different native user interface than storagecluster associated with a version of “6.1.” In some embodiments,incremental upgrades of a version may be associated with the sameversion of the native user interface. For example, version “6.1.1,”“6.1.1.d,” “6.1.2,” etc. may be associated with the same version of thenative user interface.

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided along with accompanying figures that illustrate the principlesof the invention. The invention is described in connection with suchembodiments, but the invention is not limited to any embodiment. Thescope of the invention is limited only by the claims and the inventionencompasses numerous alternatives, modifications and equivalents.Numerous specific details are set forth in the description in order toprovide a thorough understanding of the invention. These details areprovided for the purpose of example and the invention may be practicedaccording to the claims without some or all of these specific details.For the purpose of clarity, technical material that is known in thetechnical fields related to the invention has not been described indetail so that the invention is not unnecessarily obscured.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A method, comprising: receiving, at a cloudservice system, metadata associated with content stored in a pluralityof different storage domains, wherein the cloud service system receivesthe metadata associated with content stored in the plurality ofdifferent storage domains via a plurality of persistent connectionvirtualization containers, wherein each of the plurality of differentstorage domains includes a corresponding secondary storage cluster,wherein a first persistent connection virtualization container of theplurality of persistent connection virtualization containers maintainsbidirectional communications between the cloud service system and afirst secondary storage cluster associated with a first storage domainof the plurality of different storage domains and a second persistentconnection virtualization container of the plurality of persistentconnection virtualization containers maintains bidirectionalcommunications between the cloud service system and a second secondarystorage cluster associated with a second storage domain of the pluralityof different storage domains, wherein the first secondary storagecluster provides to the cloud service system via the first persistentconnection virtualization container, first metadata associated withcontent stored in a first primary storage system to which the firstsecondary storage cluster is associated and second metadata associatedwith content stored in the first secondary storage cluster and thesecond secondary storage cluster provides to the cloud service systemvia the second persistent connection virtualization container, thirdmetadata associated with content stored in a second primary storagesystem to which the second secondary storage cluster is associated andfourth metadata associated with content stored in the second secondarystorage cluster; storing and indexing together, at the cloud servicesystem, the first metadata associated with content stored in the firstprimary storage system, the second metadata associated with contentstored in the first secondary storage cluster, the third metadataassociated with content stored in the second primary storage system, andthe fourth metadata associated with content stored in the secondsecondary storage cluster; and providing, at the cloud service system, aunified metadata search interface for metadata associated with contentstored in the first primary storage system, the second primary storagesystem, the first secondary storage cluster, and the second secondarystorage cluster.
 2. The method of claim 1, wherein first secondarystorage cluster and the second secondary storage cluster are registeredwith the cloud service system.
 3. The method of claim 2, wherein thecloud service system includes a user interface service virtualizationcontainer, wherein the user interface service virtualization containeris configured to provide a user interface, wherein the user interfaceincludes the unified metadata search interface.
 4. The method of claim1, wherein the first metadata associated with content stored in thefirst primary storage system includes metadata associated with one ormore objects stored in the first primary storage system.
 5. The methodof claim 1, wherein the first metadata associated with content stored inthe first primary storage system includes metadata associated with oneor more objects backed up from the first primary storage system to thefirst secondary storage cluster.
 6. The method of claim 1, wherein themetadata associated with content received from the plurality ofdifferent storage domains is received according to an update policy. 7.The method of claim 1, wherein providing the unified metadata searchinterface further includes: receiving a request for one or more objectsbased on one or more metadata attributes; determining one or moreindexed objects matching the one or more metadata attributes; andproviding an indication of the one or more indexed objects satisfyingthe request.
 8. The method of claim 7, wherein the indication includes acorresponding location associated with the one or more indexed objectssatisfying the request.
 9. The method of claim 8, wherein thecorresponding location includes a storage domain of the differentstorage domains.
 10. The method of claim 9, wherein the correspondinglocation includes a primary storage system of the storage domain. 11.The method of claim 9, wherein the corresponding location includes asecondary storage cluster of the storage domain.
 12. The method of claim1, wherein the different storage domains are remote from each other. 13.The method of claim 1, wherein the second metadata associated withcontent stored in the first secondary storage cluster is organized usinga tree data structure.
 14. A system, comprising: a processor configuredto: receive, at a cloud service system, metadata associated with contentstored in a plurality of different storage domains, wherein the cloudservice system receives the metadata associated with content stored inthe plurality of different storage domains via a plurality of persistentconnection virtualization containers, wherein each of the plurality ofdifferent storage domains includes a corresponding secondary storagecluster, wherein a first persistent connection virtualization containerof the plurality of persistent connection virtualization containersmaintains bidirectional communications between the cloud service systemand a first secondary storage cluster associated with a first storagedomain of the plurality of different storage domains and a secondpersistent connection virtualization container of the plurality ofpersistent connection virtualization containers maintains bidirectionalcommunications between the cloud service system and a second secondarystorage cluster associated with a second storage domain of the pluralityof different storage domains, wherein the first secondary storagecluster provides to the cloud service system via the first persistentconnection virtualization container, first metadata associated withcontent stored in a first primary storage system to which the firstsecondary storage cluster is associated and second metadata associatedwith content stored in the first secondary storage cluster and thesecond secondary storage cluster provides to the cloud service systemvia the second persistent connection virtualization container, thirdmetadata associated with content stored in a second primary storagesystem to which the second secondary storage cluster is associated andfourth metadata associated with content stored in the second secondarystorage cluster; store and index together, at the cloud service system,the first metadata associated with content stored in the first primarystorage system, the second metadata associated with content stored inthe first secondary storage cluster, the third metadata associated withcontent stored in the second primary storage system, and the fourthmetadata associated with content stored in the second secondary storagecluster; and provide, at the cloud service system, a unified metadatasearch interface for metadata associated with content stored in thefirst primary storage system, the second primary storage system, thefirst secondary storage cluster, and the second secondary storagecluster; and a memory coupled to the processor and configured to providethe processor with instructions.
 15. The system of claim 14, wherein thefirst metadata associated with content stored in the first primarystorage system includes metadata associated with one or more objectsstored in the first primary storage system.
 16. The system of claim 14,wherein the first metadata associated with content stored in the firstprimary storage system includes metadata associated with one or moreobjects backed up from the first primary storage system to the firstsecondary storage cluster.
 17. The system of claim 14, wherein themetadata associated with content received from the plurality ofdifferent storage domains is received according to an update policy. 18.The system of claim 14, wherein to provide the unified metadata searchinterface, the processor is further configured to: receive a request forone or more objects based on one or more metadata attributes; determineone or more indexed objects matching the one or more metadataattributes; and provide an indication of the one or more indexed objectssatisfying the request.
 19. The system of claim 18, wherein theindication includes a corresponding location associated with the one ormore indexed objects satisfying the request.
 20. The system of claim 19,wherein the corresponding location includes a storage domain of thedifferent storage domains.
 21. A computer program product, the computerprogram product being embodied in a non-transitory computer readablestorage medium and comprising instructions for: receiving, at a cloudservice system, metadata associated with content stored in a pluralityof different storage domains, wherein the cloud service system receivesthe metadata associated with content stored in the plurality ofdifferent storage domains via a plurality of persistent connectionvirtualization containers, wherein each of the plurality of differentstorage domains includes a corresponding secondary storage cluster,wherein a first persistent connection virtualization container of theplurality of persistent connection virtualization containers maintainsbidirectional communications between the cloud service system and afirst secondary storage cluster associated with a first storage domainof the plurality of different storage domains and a second persistentconnection virtualization container of the plurality of persistentconnection virtualization containers maintains bidirectionalcommunications between the cloud service system and a second secondarystorage cluster associated with a second storage domain of the pluralityof different storage domains, wherein the first secondary storagecluster provides to the cloud service system via the first persistentconnection virtualization container, first metadata associated withcontent stored in a first primary storage system to which the firstsecondary storage cluster is associated and second metadata associatedwith content stored in the first secondary storage cluster and thesecond secondary storage cluster provides to the cloud service systemvia the second persistent connection virtualization container, thirdmetadata associated with content stored in a second primary storagesystem to which the second secondary storage cluster is associated andfourth metadata associated with content stored in the second secondarystorage cluster; storing and indexing together, at the cloud servicesystem, the first metadata associated with content stored in the firstprimary storage system, the second metadata associated with contentstored in the first secondary storage cluster, the third metadataassociated with content stored in the second primary storage system, andthe fourth metadata associated with content stored in the secondsecondary storage cluster; and providing, at the cloud service system, aunified metadata search interface for metadata associated with contentstored in the first primary storage system, the second primary storagesystem, the first secondary storage cluster, and the second secondarystorage cluster.